</para>
<para><ulink url="http://libusb.sourceforge.net">libusb</ulink>
is recommended for OS/X and Linux if you want to use a USB Garmin or
-Delorme device.
+DeLorme device.
Fedora users may need to 'yum install libusb-devel'. Ubuntu users may
need to 'yum install libusb-dev'.
</para>
You've collected a list of your favorite locations as waypoints and you'd
like to be able to share them. Unfortunately, his copy of <link linkend="fmt_gdb">Garmin Mapsource</link>
won't read data created by your copy of <link linkend="fmt_mapsend">Magellan Mapsend DirectRoute</link>. What you need
-is a program that converts data bewteen the two programs.
+is a program that converts data between the two programs.
</para>
<para>
GPSBabel actually solves that problem for you and much more...
command each time. If 'mystyle' is a format
that describes a popular program or is likely to be of use to others, you can
then share <filename>mystyle.style</filename> with other GPSBabel users.
-Send it along with a coherent description to the GPSBabel-misc mailing
+Send it along with a coherent description to the GPSBabel-Misc mailing
list for consideration to be included in a future version.
</para>
</section>
<title>GPSBabel Behavior Directives</title>
<para>
There are a few available directives to control some of the internal
-processing functions of GPSbabel.
+processing functions of GPSBabel.
</para>
<section id="style_behave_shortlen">
<title>SHORTLEN</title>
<section id="style_def_nettime">
<title>NET_TIME</title>
<para>
- Microsoft dot net represents times in 100 nanoscond intervals since midnight
+ Microsoft dot net represents times in 100 nanosecond intervals since midnight
Jan 1/0001 GMT, giving absurdly large numbers like 633943150010000000 for
mid-November, 2009. NET_TIME is how to represent those in GPSBabel.
</para>
<section id="style_def_pathspeed">
<title>PATH_SPEED</title>
<para>
- Speed in meters per second. Gpsbabel does NOT calculate this data by
+ Speed in meters per second. GPSBabel does NOT calculate this data by
default; it is read from the input file if present. (If not present,
it may be calculated with the <link linkend="filter_track">track</link>
filter.)
<section id="style_def_pathcourse">
<title>PATH_COURSE</title>
<para>
- Course in degrees. Gpsbabel does not calculate this data by default;
+ Course in degrees. GPSBabel does not calculate this data by default;
it is read from the input file if present. (If not present, it may be
calculated with the <link linkend="filter_track">track</link> filter.)
</para>
format and create a new file <filename>/tmp/geocaching.gpx</filename> in GPX format. It's important to note that the names have nothing to do with the formats actually used.</para>
<para> This command will read from a Magellan unit attached
to the first serial port on a Linux system (device names will
- vary on other OSes; typically COMx: on WIndows) and write them as a geocaching loc file.</para>
+ vary on other OSes; typically COMx: on Windows) and write them as a geocaching loc file.</para>
<example id="linux_download_from_magellan">
<title>Command showing Linux download from Magellan serial and writing to .loc file</title>
<para><userinput>gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc</userinput></para>
always result in a list of waypoints, not the original track.
</para>
<para> The presence of <parameter moreinfo="none">-s</parameter> on the command line tends to
- creats havoc on tracks and routes since many of these formats
+ create havoc on tracks and routes since many of these formats
rely on internal linkages between such points and renaming
them may break those linkages. In general, don't use
<parameter moreinfo="none">-s</parameter> when tracks or
Only the filename specified by that option will be used.
</para>
<para>
- There may be situations where predefined values are not useable
+ There may be situations where predefined values are not usable
(i.e. wrapper applications using GPSBabel in the background).
The inifile mechanism can be disabled with an empty filename.
</para>
before this one.</para>
<para>This command line reads route.gpx and replaces each point with other two
-points: one 25 metres before and another 25 metres after the original
+points: one 25 meters before and another 25 meters after the original
point. It replaces a point only if there is a change of direction
larger than 5 degrees.</para>
<para>
This option discards points that have shortnames that match the
-provided regular expresision.
+provided regular expression.
</para>
<example id="discarding_points_with_names">
<title>Discarding specific point by regular expression</title>
<para>
This option computes a value for the GPS speed at each trackpoint.
This is most useful with trackpoints from formats that don't support
-speed information or for trackoints synthesized by the
+speed information or for trackpoints synthesized by the
<link linkend="filter_interpolate">interpolate</link>
filter.</para>
<para>
<para> There are a billion variants of Comma Separated Value
-data. This is the one specifically that makes <ulink url="http://www.delorme.com">Delorme</ulink> <productname>S&A Deluxe 9</productname> happy. It's
+data. This is the one specifically that makes <ulink url="http://www.delorme.com">DeLorme</ulink> <productname>S&A Deluxe 9</productname> happy. It's
also a very simple program and useful for many other programs like
spreadsheets, but contains only a very minimal information. For general
purpose use, you'll probably be more happy with our
</para>
<example id="pn-40-send">
- <title>Command to send a pocket query (GPX) to a Delorme PN device </title>
+ <title>Command to send a pocket query (GPX) to a DeLorme PN device </title>
<para>
<userinput>
gpsbabel -i gpx -f "My Caches.gpx" -o delbin -F usb:
<para>
If you receive a message that the device is busy, especially on Windows,
- that could be because another program, likely Delorme's own, has the
+ that could be because another program, likely DeLorme's own, has the
device open even though it's not actively interacting with the GPS. In
Topo 8, on the GPS tab, look for GPS Options. Uncheck "Start GPS" and
"Automatically detect GPS". Then just click the Exchange button when
- you're ready for Topo to interact with the GPS. Other Delorme software may
+ you're ready for Topo to interact with the GPS. Other DeLorme software may
be similar.
</para>
<para>
<member> - Description</member>
<member> - Latidude</member>
<member> - Longitude</member>
- <member> - Altitude (metres)</member>
+ <member> - Altitude (meters)</member>
<member> - Date (yyyymmdd/yymmdd)</member>
<member> - Time of day (hhmmss)</member>
</simplelist>
<para>
- The format garmin_gpi supports the binary POI (.gpi) files that are useable
+ The format garmin_gpi supports the binary POI (.gpi) files that are usable
on newer Garmin GPS receivers. See <link linkend="fmt_garmin_poi">garmin_poi</link> for additional information about Garmin's own Poiloader program.
<ulink url="http://www.garmin.com/support/agree.jsp?id=927">Garmin POI-Loader</ulink> is the standard application that creates GPI files
with all possible features.
If a waypoint name is annotated with a trailing '@'NNN where NNN is
a number, that number will be used as the speed for POI alerts, just
as with Garmin's POI Loader program. The units default to metric kilometers
- per hour, but this cn be changed to statute via the units argument.
- A speed associated with a specific POI will get precdence over any
+ per hour, but this can be changed to statute via the units argument.
+ A speed associated with a specific POI will get precedence over any
'speed' argument provided. For example, a waypoint named "Point@30" will
associate a speed of 30 km/h with that specific point even if 'speed=40m'
is present in the output arguments.
receivers in Garmin protocol mode. For units like Nuvi, Zumo, or
Streetpilot, just choose a file that's on the drive where your
GPS is mounted. For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.)
- you must explictly put the unit in mass storage mode or mount
+ you must explicitly put the unit in mass storage mode or mount
the memory chip in an external reader and transfer the file
directly.
</para>
<para><userinput>gpsbabel -i globalsat,showlist=1 -f /dev/ttyUSB0</userinput></para>
</example>
<example id="globalsat-track">
- <title>Command track can be used to fetch a single track, defult is all tracks</title>
+ <title>Command track can be used to fetch a single track, default is all tracks</title>
<para><userinput>gpsbabel -i globalsat,track=number -f /dev/ttyUSB0 -o gpx,garminextensions -F outfile.gpx</userinput></para>
</example>
name, the command line option 'date' is provided.
</para>
<para>
-Conversions from gopal into any other format are a bit lossy concerning the first field of each line wich looks like an useless time tick value
+Conversions from gopal into any other format are a bit lossy concerning the first field of each line which looks like an useless time tick value
and is simply discarded while reading. If written, there will be a time_t value from the current (computed) timestamp.
</para>
<para>
<para> This is a Palm/OS file format for
<ulink url="http://www.cru.fr/perso/cc/GPilotS/">GPilotS</ulink>.
- It was tested against version 6.2 of GPilotsS
+ It was tested against version 6.2 of GPilotS
</para>
<para> Neither tracks nor routes are supported at this
time.</para>
<para>
- This is the 'gpl' format as used in Delorme mapping
+ This is the 'gpl' format as used in DeLorme mapping
products. It is a track format and contains little more than the
tracklog of a GPS that was attached while driving.
<ulink url="http://www.frontiernet.net/~werner/gps/">frontiernet.net</ulink>
1/10"; in gpx for example it is 1/100". A a practical matter, this
loss is only about 1.7 meters (5 feet).
</para>
- <para> The generated waypoint failes can also be used by MapShow
+ <para> The generated waypoint files can also be used by MapShow
version 1.14. This program is free of charge from the Holux web site.
</para>
<para> This format was contributed by Jochen Becker.
</para><para>example: E
</para></section>
<section id="ib_height"><title>HEIGHT</title><para>
-Height above sea level in metres
+Height above sea level in meters
</para><para>example: 99.859 m
</para></section>
</para></section>
<section id="ib_dist"><title>DISTANCE</title><para>
-Distance covered since last point in metres
+Distance covered since last point in meters
</para><para>example: 0.30 m
</para></section>
<para>
Google Earth 4.0 and later have a feature that can surprise users of this
format. Earth's "time slider" feature controls what timestamped data
- gets displayed. If you're using data that has timestampes (e.g. GPX
+ gets displayed. If you're using data that has timestamps (e.g. GPX
points that contain time or almost any track data) this will be important
to you. The time slider defaults to the far left position and fully closed.
This means that only the first data point will be displayed. You can
</para>
<para>
Downloaded data will be stored in data.bin file in the current
- directory together with the choosen output format. This is a rather
+ directory together with the chosen output format. This is a rather
uncommon feature in GPSBabel's formats and is likely to change in future
versions.
</para>
delimiter because it is a) supported by both OpenOffice and Ploticus
and b) is not ',', so you can use <userinput moreinfo="none">sed -i
"s/./,/g" <x>.csv'</userinput> to adapt it to locales where ',' is
- used as decimal seperator. Contributed by Tobias Minich.
+ used as decimal separator. Contributed by Tobias Minich.
</para>
<para>
When set to true, this includes Groundspeak logs from GPX pocket queries
- when writing to Delorme devices that support the extended features introduced
+ when writing to DeLorme devices that support the extended features introduced
in firmware version 2.5 for the PN-40 and PN-30 and in 1.6 for the PN-20.
</para>
</para>
<para>
If you're starting from images in another format, you may need to
- use another tool like Gimp or ImageMagick's convert to get the imaga
- into oen of the above formats to avoid errors about "Unsupported color
+ use another tool like Gimp or ImageMagick's convert to get the image
+ into one of the above formats to avoid errors about "Unsupported color
depth".
</para>
<para>
<para>
-This lets you overwride the default codec of 'windows-1252' when writing
+This lets you override the default codec of 'windows-1252' when writing
strings in Garmin GPI files. This option may be removed in future versions
of GPSBabel as it's not known which Garmin devices support which character
sets.
<para>
This option, when set, reduces the amount of whitespace in the
generated GeoJSON. This reduces the size, especially when uncompressed,
- but reduces the readibility to humans.
+ but reduces the readability to humans.
</para>
<para>
-The dump-file option is primarly for debugging is module. It lets you
+The dump-file option is primarily for debugging is module. It lets you
provide a file which contains the raw stream of bytes coming from the
device. This is useful for capturing device state to describe to a
developer that can't actually access hte physical device as well as mocking
<para>
-The showlist argment displays the list of tracks stored on the device.
+The showlist argument displays the list of tracks stored on the device.
</para>
<example id="globalsat-option-showlist">
<title>Command showing list of tracks on device</title>
of fetching all the tracks, which is our default.
</para>
<example id="globalsat-option-track">
- <title>Command track can be used to fetch a single track, defult is all tracks</title>
+ <title>Command track can be used to fetch a single track, default is all tracks</title>
<para><userinput>gpsbabel -i globalsat,track=number -f /dev/ttyUSB0 -o gpx,garminextensions -F outfile.gpx</userinput></para>
</example>
</para>
<para>
Routes and tracks without sufficient time data are always drawn as
- Linestrings and never Tracsks.
+ Linestrings and never Tracks.
</para>
<para>
Magellan's protocol specification strongly encourages the use of software
-acknowledgements on every packets. This is a simple "this is what I think
+acknowledgments on every packets. This is a simple "this is what I think
I heard. If you agree that I heard it correctly, let's go to the next packet"
handshake that is used to ensure the integrity of the data transfer.
</para>
<example id="mmo_ver">
<title>Forcing creation of old Mobile Mapper files</title>
<para>
- gpsbabel -i gpx -f whaetever.gpx -o mmo,ver=17 -F whatever.mmo
+ gpsbabel -i gpx -f whatever.gpx -o mmo,ver=17 -F whatever.mmo
</para>
</example>
disable GPRMC sentences, specify <option>gprmc=0</option>.
</para>
<para>
-GPRMC sentences contain the "recommended mimimum" positional information,
+GPRMC sentences contain the "recommended minimum" positional information,
including date and time, heading, and velocity. Note that they do not
include altitude. For altitude, you will have to include GPGGA sentences.
</para>
<para>
It the value is a set of digits then the name is fetched from a record with that field index in the .dbf file.
Otherwise, if the value does not start with a '+' character, the name is fetched from record with that field name in the .dbf file.
-When the value starts with a '+' character then multilpe records from the .dbf file can be combined to create the name.
+When the value starts with a '+' character then multiple records from the .dbf file can be combined to create the name.
The plus character should be followed by a set of digit(s) representing a field index, or a field name as above.
This may be followed by an additional '+' character, and another set of digits or a field name.
As many records as desired can be selected in this fashion.
</para>
<para>
-Consult formal eplanation of <ulink url="http://tycho.usno.navy.mil/leapsec.html">GPS time vs. UTC time</ulink> if you're into that.
+Consult formal explanation of <ulink url="http://tycho.usno.navy.mil/leapsec.html">GPS time vs. UTC time</ulink> if you're into that.
</para>
Convert route number 'index' from source into sdf format.
</para>
<para>
- We have a lot of more expressive formats thats support more than one route.
+ We have a lot of more expressive formats that support more than one route.
At this place sdf files are limited to only one single route. With option index
you can specify which route from source should be converted.
</para>
<para>\r
GPSBabel creates route points during the transformation process named "RPTxxx" where xxx is a numeric part.</para>\r
<para>\r
-Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.\r
+Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.\r
</para>\r
<example id="transform_rptname">\r
<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>\r
</para>
<para>
This camera creates log files on the SD card in a folder name "GPSLOG" that
- are named "YYMMDDNN.LOG" wher NN increments from 00 through 99. The camera
+ are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera
appends new tracks into the current file, hence the "new track" field. When
the current file reaches about 500K, NN increments and logging continues into
the next file. Therefore, there may be multiple tracks in each log
- <para> This format is for Delorme Street Atlas USA 2004 Plus and later.
+ <para> This format is for DeLorme Street Atlas USA 2004 Plus and later.
</para>
<para> For geocachers importing data from a tool like GSAK or
Spinner, import the file twice in XData. One will create a file with
<para>
-This format reads route files from many Delorme mapping products.
+This format reads route files from many DeLorme mapping products.
It supports the anr, rte, and rtd formats as either tracks or
routes.</para>
<para> All options only apply to route files from newer (anr)
This format supports the .sdf files from the Suunto product family
'Suunto Trek Manager', 'Suunto Ski Manager' and 'Suunto Sail Manager'.
The contents of the sdf file depends on the used product and can
- be one route or one track. Thats why when you want to use sdf on the
+ be one route or one track. That's why when you want to use sdf on the
output side you have to use the
<link linkend="Route_And_Track_Modes">-r OR the -t</link> option. This will tell
GPSBabel which type of data should be written.
type can store links other than web links, anything that is not a http
url will be discarded. Note that this does not do datum conversions,
so if your input file does not have WGS84/NZGD2000 data, your output
-file won't either. Colour of waypoint icons defaults to red.</para>
+file won't either. The color of waypoint icons defaults to red.</para>
- <para>Delorme TopoUSA/XMap Conduit is one of the bazillion
+ <para>DeLorme TopoUSA/XMap Conduit is one of the bazillion
<link linkend="fmt_csv">CSV variants</link>
-variants mentioned above. It's just like Delorme Streets & Atlas with the addition of
+variants mentioned above. It's just like DeLorme Streets & Atlas with the addition of
a completely pointless line at the beginning and end of the file. This
is the format used to hot-sync to XMap from withing TopoUSA. Done with
help of Dan Edwards.</para>
- <para>Delorme XMap2006 Conduit is just like
+ <para>DeLorme XMap2006 Conduit is just like
<link linkend="fmt_xmap">XMap</link>
, except there are
no spaces between fields and the coordinate format is slightly
<para>
-Delorme XMapHandHeld Street Atlas USA is another of the
+DeLorme XMapHandHeld Street Atlas USA is another of the
billion <link linkend="fmt_csv"> CSV variants</link>.
This is the format used by XmapHH SA USA on (at least) PocketPC O/S.
</para>
and XMapHH for Palm.
</para>
<para>
-Delorme XMap Handheld .WPT for PocketPC is a bit of a kludge. This
+DeLorme XMap Handheld .WPT for PocketPC is a bit of a kludge. This
chapter covers XMap Handheld Street Atlas USA edition.
</para>
<para>
XMap on the PocketPC stores its waypoints in individual .wpt files.
For example, waypoints generated by XMap on the PocketPC are stored
by default in the "My Documents" folder using the sequential names
-"XMap1.wpt", "XMap2.wpt", ad nauseum. Needless to say, this is not very
+"XMap1.wpt", "XMap2.wpt", ad nauseam. Needless to say, this is not very
efficient.
</para>
<para>